Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages
  are release-note ready, emphasizing
  what was changed, not how.
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High) - n/a
• Highlights breaking API changes (if applicable) - n/a
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___) - n/a
• Includes product update to be announced in the next stable release notes - n/a

What does this PR do?

Previously in the TS -> Go call performed by the uv plugin, JSON errors were assumed to be on stdout. However, from some testing they appear to be written to stderr, at least in the tests I've performed. This PR updates the error handling to check both sources.

How should this be manually tested?

In a uv project, add or remove a dependency in the pyproject.toml without updating the uv.lock. If you then run snyk monitor you should see the following error:

Monitoring <path/to/uv/project>...

{
  "ok": false,
  "error": "uv.lock is out of sync with pyproject.toml. Run `uv lock` to update the lockfile, or re-run with `--strict-out-of-sync=false` to test the outdated lockfile regardless.",
  "path": "/Users/thomasschafer/Development/Work/uv-goof/workspace"
}

On this branch you should instead see:

Monitoring <path/to/uv/project>...

uv.lock is out of sync with pyproject.toml. Run `uv lock` to update the lockfile, or re-run with `--strict-out-of-sync=false` to test the outdated lockfile regardless.

What's the product update that needs to be communicated to CLI users?

None